exchange server

Change page: < 1 2 3 4 5 6 7 8 9 10 11 > | Displaying page 1 of 11, items 1 to 50 of 547.

Microsoft Exchange Server 2013 : Working with cmdlets (part 2) - Understanding cmdlet errors, Using cmdlet aliases

For ease of use, Windows PowerShell lets you create aliases for cmdlets. An alias is an abbreviation for a cmdlet that acts as a shortcut for executing the cmdlet. For example, you can use the alias gsv instead of the cmdlet name Get-Service.

Microsoft Exchange Server 2013 : Working with cmdlets (part 1) - Using Windows PowerShell cmdlets, Using cmdlet parameters

Cmdlets provide the basic foundation for working with a computer from within the Windows PowerShell. Although there are many different cmdlets with many different available uses, cmdlets all have common features, which I’ll examine in this section.

Microsoft Exchange Server 2013 : Using Windows PowerShell (part 2) - Running and using cmdlets, Running and using other commands and utilities

Windows PowerShell introduces the concept of a cmdlet (pronounced commandlet). A cmdlet is the smallest unit of functionality in Windows PowerShell. You can think of a cmdlet as a built-in command. Rather than being highly complex, most cmdlets are quite simple and have a small set of associated properties.

Microsoft Exchange Server 2013 : Using Windows PowerShell (part 1) - Running and using Windows PowerShell

Windows PowerShell is built into Windows 8, Windows Server 2012, and later releases of the Windows operating system. Windows PowerShell has both a command-line environment and a graphical environment for running commands and scripts.

Microsoft Exchange Server 2013: Configuring mailbox delivery restrictions, permissions, and storage limits (part 4) - Setting storage restrictions on mailbox and archives

In a standard configuration of Exchange Online, each licensed user gets 25 GB of mailbox storage, and a storage warning is issued when the mailbox reaches 22.5 GB.

Microsoft Exchange Server 2013: Configuring mailbox delivery restrictions, permissions, and storage limits (part 3) - Permitting others to access a mailbox

Occasionally, users need to access someone else’s mailbox, and in certain situations, you should allow this. For example, if John is Susan’s manager and Susan is going on vacation, John might need access to her mailbox while she’s away.

Microsoft Exchange Server 2013: Configuring mailbox delivery restrictions, permissions, and storage limits (part 2) - Setting message send and receive restrictions on individual mailboxes

You can select multiple recipients at the same time. To select multiple recipients individually, hold down the Ctrl key and then tap or click each recipient that you want to select. To select a sequence of recipients, select the first recipient, hold down the Shift key, and then tap or click the last recipient.

Microsoft Exchange Server 2013: Configuring mailbox delivery restrictions, permissions, and storage limits (part 1) - Setting message size restrictions on delivery to and from individual mailboxes

Message size restrictions control the maximum size of messages that can be sent or received in the Exchange organization. With Exchange Online, the maximum size of messages that users can send is 35,840 KB and the maximum size of messages that users can receive is 36,864 KB by default.

Microsoft Exchange Server 2013: Moving mailboxes (part 3) - Performing on-premises mailbox moves

With online moves and batch migrations, you can move mailboxes between databases on the same server. You also can move mailboxes from a database on one server to a database on another server regardless of whether the servers are in a different Active Directory site or in another Active Directory forest.

Microsoft Exchange Server 2013: Moving mailboxes (part 2) - Performing on-premises mailbox moves and migrations

The destination database for an on-premises mailbox move can be on the same server, on a different server, in a different domain, or in a different Active Directory site.

Microsoft Exchange Server 2013: Moving mailboxes (part 1) - Importing and exporting mail data

You must have the Mailbox Import Export role to be able to import or export mailbox data. Because this role isn’t assigned to any role group, you must be explicitly assigned this role.

Microsoft Exchange Server 2013 - Managing mailboxes: The essentials (part 4) - Restoring online users and mailboxes, Repairing mailboxes

If you remove the Exchange Online license for an online user account, the user’s account is marked as an unlicensed account. Exchange Online deletes mailboxes from unlicensed accounts automatically after the grace period expires.

Microsoft Exchange Server 2013 - Managing mailboxes: The essentials (part 3) - Restoring on-premises users and mailboxes

When you disable or delete a mailbox, on-premises Exchange retains the deleted mailbox in the mailbox database and puts the mailbox in a disabled state. There is, however, an important distinction between disabling and deleting a mailbox, and this difference affects recovery.

Microsoft Exchange Server 2013 - Managing mailboxes: The essentials (part 2) - Configuring apps for mailboxes

With both on-premises Exchange and Exchange Online, you can add apps to the Outlook Web App interface to add functionality. Several apps are installed and made available to users by default, including the following apps created by Microsoft

Microsoft Exchange Server 2013 - Managing mailboxes: The essentials (part 1) - Viewing current mailbox size, message count, and last logon

You often need to manage user mailboxes the way you do user accounts. Some of the management tasks are intuitive and others aren’t. If you have questions, be sure to read the sections that follow.

Understanding Network Services and Active Directory Domain Controller Placement for Exchange Server 2013 (part 11)

The most recent versions of Exchange Server, as well as Active Directory, were designed to break through the constraints that had limited previous Exchange implementations.

Understanding Network Services and Active Directory Domain Controller Placement for Exchange Server 2013 (part 10)

To determine the default configuration domain controller, view the Event Viewer application log and search for Event ID 2081. The results of the Microsoft Exchange Active Directory Topology service query are listed here as well, as shown in Figure 8.

Understanding Network Services and Active Directory Domain Controller Placement for Exchange Server 2013 (part 9)

When a domain controller receives the orders to become a global catalog server, there is a period of time when the GC information replicates to that domain controller.

Understanding Network Services and Active Directory Domain Controller Placement for Exchange Server 2013 (part 8)

To understand how Exchange manages security, an analysis of Active Directory authentication is required. This information aids in troubleshooting the environment, as well as in gaining a better understanding of Exchange Server 2013 as a whole.

Understanding Network Services and Active Directory Domain Controller Placement for Exchange Server 2013 (part 7)

DNSLINT is a Microsoft Windows utility that helps administrators diagnose common DNS name resolution issues. The utility is not installed by default on Windows servers and has to be downloaded from Microsoft.

Understanding Network Services and Active Directory Domain Controller Placement for Exchange Server 2013 (part 6)

Troubleshooting is part of everyday life for administrators. DNS is no exception to this rule. Therefore, understanding how to use the following tools to troubleshoot DNS not only helps avoid mistakes when configuring DNS-related services, but also provides administrators with a useful toolbox to resolve issues.

Understanding Network Services and Active Directory Domain Controller Placement for Exchange Server 2013 (part 5)

This configuration is also helpful in stopping dangerous viruses from being spread through email. For example, dangerous scripts could potentially be attached to email, which could execute as soon as the user opens the mail.

Understanding Network Services and Active Directory Domain Controller Placement for Exchange Server 2013 (part 4)

Though DNS entries for MX records can be pointed to CNAME host records, doing so is not advised and is not a Microsoft recommended best practice. Increased administrative overhead and the possibility of misrouted messages can result.

Understanding Network Services and Active Directory Domain Controller Placement for Exchange Server 2013 (part 3)

Copying the DNS database from one server to another is accomplished through a process known as a zone transfer. Zone transfers are required for any zone that has more than one name server responsible for the contents of that zone.

Understanding Network Services and Active Directory Domain Controller Placement for Exchange Server 2013 (part 2)

A Windows Server 2008 or Windows 2012 DNS server can store zone information in two distinct formats: Active Directory–integrated or standard text file.

Understanding Network Services and Active Directory Domain Controller Placement for Exchange Server 2013 (part 1)

With Microsoft Exchange relying on Active Directory and domain name system (DNS) to function, it is important for an organization to make sure that critical networking services are configured and operating properly and that domain controllers have been deployed and configured to adequately support the environment.

Microsoft Exchange Server 2013 : Mailbox management - Resource mailboxes (part 2) - Processing meeting requests according to policy

The AutomateProcessing property of a room mailbox tells the Resource Booking Attendant how to handle incoming meeting requests within the structure established by the booking policy for the mailbox.

Microsoft Exchange Server 2013 : Mailbox management - Resource mailboxes (part 1) - Providing policy direction to the Resource Booking Attendant

Another important property is shown on the Resource General tab. When you enable the Resource Booking Attendant, you instruct Exchange that the attendant should monitor incoming meeting requests for the room to decide whether the requests should be accepted.

Microsoft Exchange Server 2013 : Mailbox management - Mail-enabled contacts, Mail users

Mail-enabled contacts are a convenient way to add external correspondents (people who have email accounts outside your Exchange organization) to the GAL.

Microsoft Exchange Server 2013 : Mailbox management - Moderated recipients (part 2) - Processing moderation requests, Moderated mailboxes

Provided that a supported client is used (Outlook 2013, Outlook 2010, or Outlook Web App; other clients do not include the necessary UI), the process is very straightforward and requires only a simple click from the moderator to allow the message to proceed.

Microsoft Exchange Server 2013 : Mailbox management - Moderated recipients (part 1) - Moderated groups

Many companies use distribution groups as a convenient way of communicating with large audiences. It is very convenient to be able to send a message and have it delivered to many people, but sometimes you want to ensure that only appropriate content is sent to large distributions.

Microsoft Exchange Server 2013 : Mailbox management - Shared mailboxes , Recalling messages

Exchange clients have offered users the ability to recall a sent message for many years. Unfortunately, this feature seldom works.

Migrating to Exchange Server 2007 : Migrating from Exchange 2000 Server or Exchange Server 2003 to Exchange Server 2007 (part 7)

After a new Exchange 2007 server is added to the network to functionally replace an old Exchange 2000 or 2003 server, there comes a time when the old server should be removed.

Migrating to Exchange Server 2007 : Migrating from Exchange 2000 Server or Exchange Server 2003 to Exchange Server 2007 (part 6)

Just as mailboxes are migrated from Exchange 2000 or 2003 servers to Exchange 2007 systems, public folders need to be replicated before retiring the old Exchange 2000 or 2003 servers.

Migrating to Exchange Server 2007 : Migrating from Exchange 2000 Server or Exchange Server 2003 to Exchange Server 2007 (part 5) - Moving Mailboxes

After a new Exchange 2007 server has been inserted into an existing Exchange 2000 or 2003 organization, the movement of mailboxes from an old Exchange back-end server to a new Exchange 2007 Mailbox server is as simple as selecting the mailbox or mailboxes, and through a few mouse clicks, selecting the new destination server.

Migrating to Exchange Server 2007 : Migrating from Exchange 2000 Server or Exchange Server 2003 to Exchange Server 2007 (part 4) - Installing Exchange Server 2007 on a Server System

After the Exchange 2007 prerequisites have been installed on the server that will become the Exchange 2007 system, the next step is to install the Exchange 2007 application.

Migrating to Exchange Server 2007 : Migrating from Exchange 2000 Server or Exchange Server 2003 to Exchange Server 2007 (part 3) - Installing Exchange Server 2007 Prerequisites

To install the Microsoft Management Console 3.0, with the Exchange 2007 CD or DVD Setup Wizard already active, choose the second option, which is to install the Microsoft Management Console 3.0 on the system.

Migrating to Exchange Server 2007 : Migrating from Exchange 2000 Server or Exchange Server 2003 to Exchange Server 2007 (part 2)

Whether you are performing this migration in a lab environment or in production, after performing a backup of your production environment, the first step in the migration process is to prepare the permissions in Exchange 2000 or 2003.

Migrating to Exchange Server 2007 : Migrating from Exchange 2000 Server or Exchange Server 2003 to Exchange Server 2007 (part 1) - Planning Your Migration

The planning process in migrating from an environment that has Exchange 2000 or 2003 to Exchange 2007 involves ensuring that the existing environment is ready for a migration, and that the hardware necessary to accept the migrated server roles is compatible with Exchange 2007.

Migrating to Exchange Server 2007 : Deploying a Prototype Lab for the Exchange Server 2007 Migration Process

Regardless of the method that is chosen to migrate Exchange, care should be taken to test design assumptions as part of a comprehensive prototype lab. A prototype environment can help simulate the conditions that will be experienced as part of the migration process.

Migrating to Exchange Server 2007 : Moving to Native Mode in Exchange

For an organization that previously had Exchange Server 5.5 in their environment, or possibly still has Exchange 5.5 servers in the environment, before the migration to Exchange 2007 can begin, the organization must remove all Exchange 5.5 servers.

Migrating to Exchange Server 2007 : Understanding What’s New and What’s Different with Exchange Server 2007

This section covers what is new and what is different with Exchange 2007, not from a product function and feature basis, but rather how certain changes in Exchange 2007 impact the migration process to Exchange 2007.

Migrating to Exchange Server 2007 : Understanding How to Migrate to Exchange Server 2007

For larger organizations, the various server roles will likely be applied to systems dedicated to a particular server role for purposes of performance and scalability. In many cases, a larger organization will already have existing roles for front-end and back-end servers, as well as bridgehead servers.

Microsoft Exchange Server 2013 : Mailbox management - Setting mailbox permissions (part 5) - Outlook delegate access

Apart from the control an administrator can exercise over mailbox access, Outlook users can also control access by using the Delegate Access option, found in the backstage area for Outlook 2013.

Microsoft Exchange Server 2013 : Mailbox management - Setting mailbox permissions (part 4) - Sending messages on behalf of other users

If you plan to send messages on behalf of other users, you should enable the From field in the client interface so that users can select the mailbox from which they want to send the message.

Microsoft Exchange Server 2013 : Mailbox management - Setting mailbox permissions (part 3) - Mailbox auto-mapping through Autodiscover

Granting Full Access to a mailbox is one thing; a user being able to open the mailbox to access it is quite another. The traditional approach has been to modify the user’s Outlook profile so that the mailbox is opened along with the other resources available to the user.

Microsoft Exchange Server 2013 : Mailbox management - Setting mailbox permissions (part 2) - Managing Full Access permission

Assigning Send As permission for a mailbox enables a user to impersonate someone else, but apart from being able to create and send messages, the Send As permission does not grant any further access to mailbox contents.

Microsoft Exchange Server 2013 : Mailbox management - Setting mailbox permissions (part 1) - Mailbox delegation

The ability to change the way messages are processed in a mailbox became a fundamental part of email system functionality a long time ago.

Microsoft Exchange Server 2013 : Mailbox management - Health mailboxes

Exchange 2013 includes a new Managed Availability feature that is incorporated in the system architecture so Exchange can detect and resolve common problems caused by malfunctioning components

Microsoft Exchange Server 2013 : Mailbox management - Discovery mailboxes - Creating additional discovery mailboxes

Discovery mailboxes are used as the repository for the metadata that drives eDiscovery searches and the output the searches generate from user mailboxes.